reportDeprecation() dedups per api+detail and logs at trace level by
default; NS_DEPRECATIONS=warn|error previews the stricter stages so the
same call sites can be escalated over releases. Wired at the external
entry points only: param-name hook invocation, require-time extension
registration, and dynamicCall help templating.

A class migrated off property injection has neither $hooksService nor
$injector, so the decorator threw at hook-execution time. The global
injector must stay last in the chain - tests stub the instance
properties and rely on them winning.

Yok keeps its entire public surface, subclassability, and the global
$injector, while storage and resolution delegate to the new container.
Command routing, key commands, and the public-API builder are unchanged.
Every legacy member now carries @deprecated JSDoc naming its
replacement, mirrored on IInjector.

DoctorService and ProjectNameService become @contract abstract classes;
their impls are renamed *Impl (externally invisible - outside resolution
is by string name or token, never class identity). The subpath resolves
through contracts/package.json rather than an exports map, so existing
deep requires keep working, and the entry point is side-effect-free so a
duplicated CLI copy in an extensions tree never boots a second runtime.

Fixtures exercise the surfaces third parties rely on: param-name hook
signatures across every payload shape and influence channel (mutation,
function-return middleware, abort), require-time extension registration
against global.$injector including hierarchical commands, and the full
IInjector facade surface. Notably they pin that a hook naming an
unwrapped payload key (the after-watchAction shape) is skipped as
invalid - resolution changes must not resurrect long-dead hooks.

dependency-injection.md covers tokens (@contract), inject()/Injector,
provider kinds, resolution semantics, forwardRef, coexistence with the
legacy $injector, and a legacy-to-new quick reference. extending-cli.md
leads with the recommended hook pattern - inject() works directly in
hook bodies because they run in an injection context, pinned by a new
compat test - and demotes parameter-name injection to a labeled legacy
section. String-token lookups are framed as the migration bridge, not a
co-equal API.

The hook deprecation tracer now flags only hooks that actually use
param-name service injection; a hookArgs-only signature follows the
recommended pattern and stays silent.

Internal code no longer reads global.$injector: the two cycle-bound
sites (the deprecation tracer's logger fallback and @hook's last-resort
lookup) go through a getInjector() accessor required at call time. The
global property remains write-only from the CLI's side - it exists as
the published surface for extensions and hooks.

IInjector recomposes from per-subsystem faces - CommandRegistry,
KeyCommandRegistry, ModuleRegistry, PublicApiBuilder - each an @contract
token the facade registers itself under. One object still implements
everything until the subsystems are physically extracted; extraction
then becomes a provider swap for the face's token instead of a consumer
migration. Consumers can depend on the narrow face they actually use,
and deprecation becomes per-face instead of a flat everything-is-legacy.

The contracts are internal (lib/common/contracts) and deliberately not
re-exported from nativescript/contracts; promoting one is a per-contract
decision.

- doctor-service: printWarnings accepts an optional trackResult matching
  its contracts; runSetupScript returns the setup script result instead
  of resolving undefined; canExecuteLocalBuild no longer dereferences
  its optional argument
- deprecation tracer: a report dropped for lack of a logger is no
  longer latched as delivered - it reports once a logger exists
- yok: global.$injector is an accessor pair, so a direct third-party
  assignment stays synchronized with the binding getInjector() reads
- docs: note the useValue + shared:false quirk; show where Injector is
  imported from in the late-lookup example

…adapter

Commands can now be declared as plain objects: a name, an option schema
built from booleanOption/stringOption/numberOption/arrayOption, and a run
function whose context carries the positional args plus the declared
options, typed by inference from the schema.

lib/common/define-command holds the types and the pure factories only, so
it stays side-effect-free and can be re-exported from
nativescript/contracts. The runtime bridge lives in
lib/common/services/command-definition-adapter, which compiles a
definition into the ICommand the legacy registry expects and runs it
inside an injection context.

canExecute is emitted only when the definition supplies one or opts into
arguments: "any"; CommandsService skips all parameter validation as soon
as canExecute exists, so omitting it is what lets the framework reject
stray positional arguments for arguments: "none".

Fully additive — existing ICommand classes are untouched.

…nitions

A definition with no declared options must be executable in a container
that has no options service registered - manifest-loaded extension
commands run in exactly that situation.

The parent-dispatcher leak onto the module-level injector is fixed in
the base branch, so the round-trip test no longer needs the global
facade.

Yok extends Injector on the base branch; the di bridge is gone.